Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Since we have a node view in the bootstrap that is not inserted into the P2P MemTable, we cannot rely on the MemTable field
availability_history
to know if the node is currently connected or not.So I implemented a new ets table managed by the ConnectionSupervisor and Connection module to store the current connection state of a node. So we don't rely on other thing that just the connection itself to determine if a node is connected
Type of change
How Has This Been Tested?
Unit test on
connected?
functionRunning node connecting and stopping them
Checklist: